FuzzyQuery produces a wrong result when prefix is equal to the term length #1002
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NightOwl888
approved these changes
Nov 4, 2024
There was a problem hiding this comment.
Other than the fact that the link to the original PR is not on this PR or on #941, this looks fine.
And here is the link: apache/lucene-solr#1545
|
@NightOwl888 Thanks for finding the PR, I only included the commit hash in the comment as that was what I had found at the time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FuzzyQuery produces a wrong result when prefix is equal to the term length
Fixes #941
Description
See #941
(NOTE: This PR was originally opened as #945 but included an unexpected commit. This PR cherry-picks that commit.)